
This example shows the effect of the priority feature on the state machine evolution
=====================================================================================


The state machine evolves first onto the shared state.

After the countdown expires, all conditions for the events:

- maxcount
- maxcount && OUT_CONDITION
- maxcount || !OUT_CONDITION

are satisfied, hence all three events happen within the shared state.

This can be observed since all of the three associated outputs: 

- EVENT1_FIRED
- EVENT2_FIRED
- EVENT3_FIRED

are activated. However since the priority of the second event (maxcount && OUT_CONDITION) is higher than the others, 
the state machine will evolve to the landing_state_2.

After the next countdown, the SCT evolves back to the entry state as the associated transition (event)
clears the OUT_CONDITION. Otherwise the other two events would have kept the SCT "trapped" into the remaining landing states 

Spefiying a priority field in the tool allows to use the property that events with a higher number will have higher priority 
over each other. So the tool automatically maps the higher priority transitions to higher event numbers
